Example 1: Meeting Summary from Single Call
Scenario: Generate professional meeting notes from a customer call1
Open the Recording
Navigate to your Recordings and open the call you want to summarize
2
Start Document Generation
From the call details page:
- Click the Generate button (or ••• menu)
- Select “Generate Document”
3
Choose Template
Select Meeting Summary template
4
Verify Data Source
The call should already be selected as the source
5
Configure Generation
- Title (optional): “Acme Corp Q1 Review”
- Focus (optional): “Highlight action items and next steps”
- Generation Style: Focused Analysis (default for single call)
- Data Format: Full Context (uses complete transcript)
- Visibility: Private or Workspace
6
Generate
- Click “Create Document”
- Wait 30-60 seconds
- Document opens automatically when ready
Example 2: PRD from Multiple Customer Calls
Scenario: Create a product requirements document from 5 customer interviews about the same feature1
Organize Calls in Folder
- Create a folder called “API Integration Feedback”
- Add all 5 related customer calls to the folder
2
Create Document from Folder
- Go to Documents section
- Click “Create Document”
3
Choose PRD Template
Select Product Requirements Document template
4
Add Data Sources
In the Data step:
- Click “Folders” tab
- Select your “API Integration Feedback” folder
- All 5 calls are now included
5
Configure Generation
- Title: “API Integration Feature Requirements”
- Focus: “Extract technical requirements, integration needs, and user pain points for API development”
- Generation Style: Theme Discovery (for multiple calls)
- Data Format: Full Context
- Visibility: Workspace
6
Generate and Edit
- Click “Create Document”
- Wait 1-2 minutes for processing
- Review generated PRD
- Edit directly in the document editor
- Use document chat for refinements
Theme Discovery mode is best for multiple calls - it identifies patterns and themes across all conversations.
Example 3: Weekly Feature Request Report
Scenario: Create a document summarizing all feature requests from the past week1
Filter Signals
- Go to Signals section
- Filter: Type = “Feature Request”
- Filter: Date = “Last 7 days”
- Filter: Interaction = “External”
2
Save as Dataset
- Click “Save as Dataset”
- Name: “Weekly Feature Requests”
3
Generate Document from Dataset
- Go to Documents section
- Click “Create Document”
- Choose template (e.g., “Status Update” or custom report template)
4
Add Dataset as Source
- In Data step, click “Datasets” tab
- Select “Weekly Feature Requests” dataset
5
Configure
- Title: “Weekly Feature Request Report - [Date]”
- Focus: “Group by customer account and prioritize by frequency”
- Generation Style: Theme Discovery
- Data Format: Key Insights (using signals)
- Visibility: Workspace
6
Generate and Share
- Generate document
- Review and edit as needed
- Copy to share in Slack/email
- Or share BuildBetter link with team
Example 4: Customer Feedback Summary (Multiple Sources)
Scenario: Combine calls, support tickets, and survey responses into one comprehensive report1
Prepare Sources
Create a folder called “Q1 Customer Feedback” containing:
- Customer calls from the quarter
- Imported Zendesk conversations
- Survey responses (if using Typeform/Pendo integration)
2
Create Document
- Go to Documents > Create Document
- Choose a report or summary template
3
Add Folder
- Select “Q1 Customer Feedback” folder as source
- All content types automatically included
4
Configure Generation
- Title: “Q1 Customer Feedback Report”
- Focus: “Identify top pain points, feature requests, and satisfaction trends. Group findings by theme.”
- Generation Style: Theme Discovery (for large dataset)
- Data Format: Key Insights
5
Generate Multi-Source Report
- Generate document
- AI analyzes across all source types
- Themes emerge from combined data
Combining multiple data source types (calls + tickets + surveys) provides a more complete view than any single source alone.
Example 5: Using Document Chat for Refinement
Scenario: The generated document is good but needs specific additions1
Open Generated Document
Open your newly created document
2
Access Document Chat
Click the chat icon in the top-right corner
3
Ask for Additions
In the chat, request specific changes:
- “Add a section about pricing concerns mentioned in the calls”
- “Extract all timeline requirements mentioned”
- “What specific API endpoints were discussed?”
4
Apply AI Suggestions
- Review AI’s response in chat
- Copy relevant content
- Paste into your document
- Edit to integrate smoothly
Document Generation Best Practices
Choose the right template: Match template to document purpose (PRD for requirements, Meeting Summary for notes)
Use appropriate generation style: Focused Analysis for 1-10 sources, Theme Discovery for 10+ sources
Provide specific focus: Detailed instructions produce better targeted content
Start with fewer sources: Test with 2-3 calls before generating from 50+
Edit after generation: AI provides a strong starting point - add your expertise
Common Document Types
Meeting Notes
- Template: Meeting Summary
- Sources: Single call
- Format: Full Context
- Use: Quick professional notes after any meeting
Product Requirements
- Template: Product Requirements Document (PRD)
- Sources: Multiple customer calls or folder
- Format: Full Context or Key Insights
- Use: Feature planning and development specs
Status Reports
- Template: Status Update
- Sources: Signal dataset or folder
- Format: Key Insights
- Use: Weekly/monthly progress reports
User Stories
- Template: User Stories
- Sources: Research calls or feedback signals
- Format: Full Context
- Use: Development planning and sprint work